home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
049a
/
mr2.zip
/
MR2.DOC
< prev
next >
Wrap
Text File
|
1992-01-03
|
10KB
|
219 lines
MR/2 - A QWK Compatible Mail Reader for OS/2
Copyright (c) 1992, Knight Writer Software Company.
All rights reserved.
===================================================================
N O T I C E
===================================================================
This is beta-level software and is incomplete and may still contain
significant bugs. Please report any and all problems to the author.
Various addresses are provided at the end of this document.
The standard "I'm not responsible" disclaimer applies - I'll supply a
real one here eventually. You know how it goes.
This IS a shareware package, and does require a registration fee if you
choose to continue using it after 30 days. At this time, since it is
incomplete and buggy, I'll extend the trial period to 60 days. By then
I'll have released a "finished" 1.0 version (finished by my definition).
The registration fee will be initially set at $12. The final product
will have a "begging" screen with a key-file that will register the
software and suppress it. I won't be chasing anyone down for not
paying, but the more interest I get, the more likely I am to continue
with improvements.
===================================================================
IF MR/2 SHOULD CRASH
===================================================================
All is not lost (at least I hope not). Just go back into MR/2 and
respond with the ENTER key when asked if you wish to use the existing
packet. If your last reply is missing (this happens if the crash is due
to a reply being filed), use the "X" command while viewing any message
to "Fast Exit" MR/2. Check for Reply.Msg in the MR2 software directory
and save it somewhere - this SHOULD be your missing reply. Reply to the
original message again and, once in your editor, use this saved file to
respond.
These problems (with replying) should be cleared up before I let MR/2
out. Still, only testing and time will tell for sure.
PRELIMINARY DOCUMENTATION
=========================
Unpack the MR2.ZIP file into an appropriate directory ("\MR2", for
instance). All MR/2 files should be kept together in the same
directory. You must invoke MR/2 only while pathed into this directory -
this is the only way that MR/2 will be able to find its supporting
files.
INSTALLATION
============
Unpacking MR2.ZIP is all that's involved in installing MR/2. You may
choose to create and edit an ".ini" parameter file for MR/2. This file
may be used to set up various run-time options. A template file,
"MR2INI.ORG" is provided that provides examples of all available
parameters along with some explainations.
NOTE: When MR/2 is invoked for the very first time (actually, any time
where the file "MR2.INI" is not found), it will allow for creation of
this file. A short prompt will ask for your permission, and if given,
the file "MR2INI.ORG" will be copied to "MR2.INI", and the OS/2 system
"E" editor will be loaded, ready for you to make any desired
modifications. Once the editor is exited, you will see the MR/2 packet
selection screen.
It is very important to identify the correct "packet path" in the
MR2.INI file. This must identify the directory in which all your .QWK
packets are kept. MR/2 includes no provisions for changing the "packet
path" on demand, short of modifying the .ini file and reloading.
The initial MR2.INI file contains documentation on each option. Examine
and set these options carefully to fit your specific needs.
GENERAL
=======
Simple help screens are available at any time by depressing F1 (or by
pressing the middle button on a three-button mouse). If you find a spot
where HELP is unavailable, please report this to the author. The package
was initially tested under OS/2 1.3, however, most later development and
testing were performed using 2.0 beta versions 6.149 and 6.167.
MR/2 was written in C++, using Zortech's 3.0 release. I used many of
the class "tools" provided by Zortech, most of which I had to modify in
one form or another. Source code is not available, however, I will
gladly offer assistance to anyone wishing to write their own reader.
I've modeled this reader, at least somewhat, after the MS-DOS SLMR
reader. It works in a similar manner, and many keystroke functions are
the same. Before I wrote MR/2, SLMR was my reader-of-choice, and I
found it to meet my needs nicely.
That's it for now as far as documentation goes. I'll supply a better
manual at a later date. I may even check for spelling errors. You'll
have to try it to learn it.
KNOWN BUGS AND STUFF - 01/03/92
===============================
Mouse support is broken. It works sometimes under the 6.149 beta, but
is totally broken under 6.167.
The TEMPORARY directory MUST remain a subdirectory of the MR2 home dir.
I don't supply an editor. You'll have to find your own or use E or EPM.
QEdit for OS/2 works nice as an inexpensive, character-mode editor
The packet path is also assumed to be the reply packet path. Your reply
packets will be placed in with your .qwk mail packets.
No FIND under NEWS - NEW FILES - BULLETIN file viewing yet. Works from
within message viewing, though. You also cannot search through all messages
in all conferences with one command.
Many .ini file parameter ideas are unfinished. Some haven't even been
started.
No tagline file, selection or automatic rotation. A single tagline is
specified in the .ini file. You can modify the tagline while editing a
message header, but any changes made will be remembered during that session
only. MR/2 reads the default tagline from the .ini file each time it loads.
No "save file" selection - a single save file is used, the name of which
is specified in the .ini file. (default is "save.txt")
Failed packing/unpacking tends to dump you on the command line.
You can't sort any of the selection lists.
No delete/rename function has been provided for packets. You'll have to
go the the command line for this.
No "bookmark" mechanism is provided. MR/2 won't know where you left off
when you reenter a packet. Also, marking messages as read, replied and
saved is implemented, but these flags are lost when you close a packet.
Subsequent reading of the same packet will not benefit from previous
flag settings.
I've tested MR/2 with Markmail and somewhat with QMail packets. Others
are untested.
You can't send ADD/DROP conference messages yet. This seems easy enough,
so I should be able to add it in soon.
ANSI support is not provided for messages or file viewing and @variables
are not converted. Sorry, maybe later.
Long replies (over 100 lines) are not split. I need more information as
to when this might be a problem.
Other frills that have not yet been addressed: Bulk marking, forwarding
messages, carbon copies, creating replies without having a source packet,
twit filter, sorted selection lists, function key assigning, changing the
packet path on demand. There are probably others. Feel free to bombard
me with requests.
You can't yet edit the .ini file via keypress from within MR/2 (no SLMR
ALT-C key).
Help files will be merged into a single .hlp file.
Quoting style is limitted to the one I use. I'll add some others
eventually.
When you kill a reply, the message remains visible but is displayed with
a "KILLED" status - it is NOT removed from view. If you load the replies
again later, the killed messages will not be displayed. Killed messages
can be saved to a file, and can also be unkilled by editing the reply
(any time you use "R" to reply to a reply, you actually edit the original
reply).
Any ideas on how to effectively use multithreading would be appreciated.
No long file name support. Since QWK is a DOS thing, the only place I can
see using it is for packet names (if the user renames it). Any ideas?
CONTACTING THE AUTHOR
=====================
You can contact me in a number of ways. Unfortunately, I can't provide
a phone number at this time.
US Mail: Nick Knight
1823 David Ave.
Parma, Ohio 44134
Fido netmail: 1:157/2 to "Nick Knight"
Fido Echomail: Echomail messages to me are discouraged, as
keeping them "on topic" and interesting to
the masses would be difficult. I do read OS2,
OS2PROG, C_PROGRAMMING, C_PLUSPLUS and DR DEBUG
daily, though. OFFLINE echo also (deals with
mail readers), this might be THE place to ask
public questions, eh?
Direct BBS: Leave a message on the Nerd's Nook BBS (157/2)
at (216) 356-1772, 356-1882 or 356-1431.
I check in here multiple times a day. I will
also keep the most recent copy of MR/2 posted
here. Other boards (non-local) will get updates
at my convenience.
Optionally, I call into PC-OHIO regularly.
Compuserve: I check in here only when I have to. Try
mail to my user ID - 76066,1240, although this
isn't the best approach.